Prioritizing multiple callers with a suggested time for a caller to call back

ABSTRACT

A computing device includes a memory; and a processing circuit coupled to the memory and configured to receive call data regarding a plurality of telephone calls placed to the computing device, each of the plurality of telephone calls being placed by a caller; prioritize each caller based on the call data and prioritization data stored in the memory, the prioritization data providing an indication of a relationship between each caller and a receiver associated with the computing device and including at least one of electronic contact data, electronic calendar data, and social media data; determine a future time for each caller to speak with the receiver based on the prioritization of each caller; and transmit a message to each caller providing an indication of the future time.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/091,885, filed Apr. 6, 2016 (now U.S. Pat. No. 9,565,300), which is acontinuation of U.S. application Ser. No. 14/569,221, filed Dec. 12,2014 (now U.S. Pat. No. 9,319,521), the entire disclosures of theforegoing applications are hereby incorporated by reference herein.

BACKGROUND

Telephone-enabled devices such as mobile phones are typically configuredto direct missed calls to a voice messaging or similar system such thata caller is able to leave a voice message for the intended recipient. Ifthe intended recipient is in a meeting, driving a car, or otherwiseunable or unwilling to answer his or her phone, multiple telephone callsmay go unanswered. Once the intended recipient is able or willing toagain utilize his or her phone, he or she may, as desired, return one ormore of the missed telephone calls.

SUMMARY

One embodiment relates to a computing device, including a memory; and aprocessing circuit coupled to the memory and configured to receive calldata regarding a plurality of telephone calls placed to the computingdevice, each of the plurality of telephone calls being placed by acaller; prioritize each caller based on the call data and prioritizationdata stored in the memory, the prioritization data providing anindication of a relationship between each caller and a receiverassociated with the computing device and including at least one ofelectronic contact data, electronic calendar data, and social mediadata; determine a future time for each caller to speak with the receiverbased on the prioritization of each caller; and transmit a message toeach caller providing an indication of the future time.

Another embodiment relates to a mobile computing device, including aprocessing circuit configured to receive call data regarding a pluralityof telephone calls placed to the computing device, each of the pluralityof telephone calls being placed by a caller; prioritize each callerbased on the call data and prioritization data, the prioritization dataproviding an indication of a relationship between each caller and areceiver associated with the mobile computing device; determine a futuretime for at least one of the callers to speak with the receiver based onthe prioritization of each caller and a predicted arrival time of themobile computing device at a destination location; and transmit amessage to at least one of the callers providing an indication of thefuture time.

Another embodiment relates to a method of prioritizing multiple callers,including receiving call data regarding a plurality of telephone callsplaced to a computing device, each of the plurality of telephone callsbeing placed by a caller; prioritizing each caller based on the calldata and prioritization data, the prioritization data providing anindication of a relationship between each caller and a receiverassociated with the computing device and including at least one ofelectronic contact data, electronic calendar data, and social mediadata; determining a future time for each caller to speak with thereceiver based on the prioritization of each caller; and transmitting amessage to each caller providing an indication of the future time.

Another embodiment relates to a method of prioritizing a plurality ofcallers, including receiving call data regarding a plurality oftelephone calls placed to a mobile computing device, each of theplurality of telephone calls being placed by a caller; prioritizing eachcaller based on the call data and prioritization data, theprioritization data providing an indication of a relationship betweeneach caller and a receiver associated with the mobile computing device;determining a future time for at least one of the callers to speak withthe receiver based on the prioritization of each caller and a predictedarrival time of the mobile computing device at a destination location;and transmitting a message to at least one of the callers providing anindication of the future time.

Another embodiment relates to a non-transitory computer-readable mediumhaving instructions stored thereon that when executed by a computerprocessor cause the computer processor to perform a method, the methodincluding receiving call data regarding a plurality of telephone callsplaced to a computing device, each of the plurality of telephone callsbeing placed by a caller; prioritizing each caller based on the calldata and prioritization data, the prioritization data providing anindication of a relationship between each caller and a receiverassociated with a mobile computing device; determining a future time forat least one of the callers to speak with the receiver based on theprioritization of each caller and a predicted arrival time of the mobilecomputing device at a destination point; and transmitting a message toat least one of the callers providing an indication of the future time.

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the drawings and the followingdetailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of a plurality of telephone-enabledcomputing devices communicatively coupled by way of a communicationsnetwork according to one embodiment.

FIG. 2 is a front view of a computing device according to oneembodiment.

FIG. 3 is a block diagram of a processing circuit of the computingdevice of FIG. 2 according to one embodiment.

FIG. 4 is a block diagram of a method for prioritizing missed telephonecallers according to one embodiment.

FIG. 5 is a block diagram of a method of prioritizing missed telephonecallers according to another embodiment.

FIG. 6 is a display of a calendar or scheduling user interface accordingto one embodiment.

FIG. 7 is a display of a messaging user interface according to oneembodiment.

FIG. 8 is a display of a missed calls user interface according to oneembodiment.

FIG. 9 is a display of a navigation system user interface according toone embodiment.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part thereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here.

Various embodiments disclosed herein relate to systems and methods forprioritizing missed telephone callers. At times, a user (e.g., receiver,intended recipient, etc.) of a telephone-enabled device (e.g., acellular phone, mobile phone, smart phone, landline phone, etc.) may beunable or unwilling to answer one or more incoming telephone calls fromvarious callers. Eventually, the receiver may wish to return one or moreof the missed telephone calls. As such, various embodiments disclosedherein relate to prioritizing callers associated with missed telephonecalls and providing an indication of a future time that may be moreconvenient for the parties to speak. The prioritization may be performedbased on various types of data, including data indicating the type orextent of the relationship between the caller and receiver. Such datamay be provided by, for example, an electronic contacts application, anelectronic calendar application, one or more messaging applications(e.g., phone, email, text messaging, etc.), and the like. Based on theprioritization, the future time may be communicated to the caller viaone or more messages (e.g., during the telephone call, via a returntelephone call, email, text message, etc.). The future time may bedetermined based on various types of data, including calendar data forthe caller and/or receiver, navigation data regarding current travel ofthe caller and/or receiver, and the like.

Referring now to FIG. 1, computing device 10 is shown communicativelycoupled to remote devices 12, 14 by way of communications network 16according to one embodiment. Devices 10, 12, 14 may include a widevariety of devices, including mobile computing devices (e.g., mobilephones, cellular phones, laptop or tablet computers, etc.), desktopcomputing devices, (e.g., linked to landline phones, using VoIP, etc.),phone-enabled computing devices integrated into other components orsystems (e.g., vehicle-based computing systems with telephonefunctionality, etc.), and the like. Network 16 may include any suitablewired or wireless communications network configured to enable cellularand/or data communications between devices (e.g., a cellular network, alocal area network, a Bluetooth or infrared communication link, theInternet, etc.).

Referring to FIG. 2, device 10 is shown in greater detail according toone embodiment. Device 10 includes housing 18, display 20, and one ormore buttons 22 (e.g., soft-buttons, bezel buttons, a keyboard, etc.).Device 10 further includes speaker 24 and microphone 26 to enabletelephone functionality for device 10. In some embodiments, device 10 isa mobile computing device, such as a laptop computer, cellular or mobilephone, and the like. In other embodiments, device 10 is communicativelycoupled to a phone-enabled device and configured to receive dataregarding telephone calls placed or received by the phone-enableddevice. Device 10 may take any suitable size or shape and providevarious functionality to users.

Referring now to FIG. 3, in one embodiment device 10 include aprocessing circuit shown as processing circuit 28. Processing circuit 28includes personal information module 30, location/navigation module 32,processor 34, memory 36, prioritization module 38, and input/outputdevices 40. It should be noted that the various components illustratedin FIG. 3 may be integrated together or separated into furthersub-components relative to those illustrated herein. Further, device 10and processing circuit 28 may in some embodiments include furthercomponents in addition to those shown in FIGS. 2-3.

Personal information module 30 includes or stores various data regardinga user of device 10, including messaging data for one or more messagingapplications 42, contacts data for electronic contact application 44,calendar data for electronic calendar application 46, and social mediadata for one or more social media applications 48. The variousapplications may run on or be accessible by device 10. Contact dataincludes various information regarding one or more contacts, including aname, address, telephone number, email address, and other contactinformation. Contact data may include a target response time forconnecting with the caller (e.g., “I want to respond to Jim within 3hours, but Sally is less important, and a 3 day response isacceptable”). The contact data may include a targeted call duration tobe allotted to a return call with the caller (e.g., “when schedulingcall backs, allot 15 minutes for calls with George, but Sam's call canbe only 2 minutes long”). Further, one or more contacts may be tagged ashigh priority contacts such that they are ordered higher thannon-priority callers on a list of callers; such priority status can beassigned to a contact either on a permanent basis, or a temporary andchangeable basis. Calendar data includes data regarding variousappointments, scheduling parameters, and the like, including indicationsof when the user is available, unavailable, and where the user isscheduled to be at various times. Calendar data may also include dataregarding or links to contact data (e.g., in cases where an appointmentis scheduled with a person in an electronic contact application, thecontact application may be accessed by way of a link provided in anelectronic calendar appointment). Social media data includes variousinformation regarding a user's affiliation with one or more social mediasites, and may further provide indications of other users that areassociated with the user of device 10 via one or more social mediasites.

The various types of data stored in personal information module 30 mayalso provide indications of a relationship between the user of device 10and various other users, e.g., potential callers. For example, storeddata may include messaging history regarding how often two users (e.g.,an owner of device 10 and another user) telephone each other, textmessage each other, email each other, and the like (including the numberof times, how recently, whether calls were missed or completed, whethermissed calls were returned and with what priority, etc.). Similarly, thestored data may provide an indication of things two users may have incommon in terms of contact data, such as a common workplace, a commonhome community, a common address or name (e.g., in the case of familymembers), and so on. Further, future and historical data forappointments between users may be stored, including dates, locations,frequency of meetings, and so on. In some embodiments, data regardingsocial media may provide indications of common social media websites forwhich two users are registered, visit while web browsing, etc.

Location/navigation module 32 in one embodiment includes locationdetermining system 50, navigation system 52, and location historydatabase 54. Location determining system 50 is configured to determine acurrent location of device 10. In one embodiment, location determiningsystem 50 includes a GPS receiver and utilizes GPS techniques todetermine a current location of device 10. In other embodiments,location determining system 50 may utilize other techniques, includingnetwork-based techniques (e.g., triangulation, etc.) and the like.Navigation system 52 is in one embodiment a navigation system configuredto provide various navigation data to users (e.g., maps on a display,audible commands or alerts, etc.) regarding a planned route from astarting point to a destination point. Location history database 54 isconfigured to store data regarding the location and/or travel of device10 at various points in time.

Referring further to FIG. 3, processing circuit 28 further includesprocessor 34 and memory 36. Processor 34 may be implemented as ageneral-purpose processor, an application specific integrated circuit(ASIC), one or more field programmable gate arrays (FPGAs), adigital-signal-processor (DSP), a group of processing components, orother suitable electronic processing components. Memory 36 is one ormore devices (e.g., RAM, ROM, Flash Memory, hard disk storage, etc.) forstoring data and/or computer code for facilitating the various processesdescribed herein. Memory 36 may be or include non-transient volatilememory or non-volatile memory. Memory 36 may include databasecomponents, object code components, script components, or any other typeof information structure for supporting the various activities andinformation structures described herein. Memory 36 may be communicablyconnected to processor 34 and provide computer code or instructions toprocessor 34 for executing the processes described herein.

Prioritization module 38 is in one embodiment configured to store dataregarding prioritizing telephone calls placed to device 10 by variouscallers. In one embodiment, prioritization module 38 includes prioritylist 56 (e.g., a database, etc.). List 56 provides a priority list ofpotential callers that may place telephone calls to device 10. List 56prioritizes, or ranks, the potential callers in an order correspondingto a desired priority in which the user of device 10 would typicallydesire to return the calls. For example, a user may prioritize a spousehigher than a coworker, a family member higher than a friend, and so on.As discussed in greater detail below, the data from priority list 56 isusable to prioritize multiple callers in cases where a user of device 10is unable or unwilling to receive a number of telephone calls (e.g., asa result of being in a meeting, travelling, away from device 10, etc.).In some embodiments, priority list 56 may be implemented by taggingcontacts in an electronic contacts application (e.g., “favorites”) suchthat callers that are tagged contacts are given higher priority callback times. Such priority tags or priority ranking can be permanent(e.g., wife is always ranked highly), or can be temporary andchangeable. In some embodiments, a caller whose call is missed, but isprioritized highly for a return call by prioritization module 38, mayadditionally be given a high priority tag; so that, for instance, if theprioritized caller places a new call before the first one is returned,prioritization module 38 ranks responding to him or her more highly.Such temporary priority tags can then be revoked after a subsequent callis completed.

Prioritization module 38 in some embodiments further includes scheduler58. Scheduler 58 may operate in combination with calendar 46. In oneembodiment, schedule 58 provide indications of time periods during whicha user will be unable or unwilling to answer telephone calls (e.g., inaddition to any time periods where calendar appointments may prevent theuser from answering telephone calls), such that processing circuit 28prioritizes any calls received during such time periods. In otherembodiments, scheduler 58 provides an indication of time periods duringwhich a user wishes to return any missed calls. For example, a user mayspecify that he or she does not want to answer any phone calls from10:00 am until 12:00 noon, and that any calls received during that timeshould be prioritized by processing circuit 28 such that the receivercan return the calls between 1:00 pm and 2:00 pm. As shown in FIG. 6, insome embodiments, a display 100 is generated by device 10 to showperiods 102 where a user is unable/unwilling to receive calls, andperiods 104, 106, 108 where a user is able to receive/return calls.According to various alternative embodiments, other types of data may bestored by prioritization module 38. In some embodiments, a user ofdevice 10 may also own, or anticipate receiving calls on, one or moreother telephone-enabled devices. Accordingly, call data and/orprioritization data may be shared between a plurality of the user'stelephone-enabled devices. Device 10 can be configured to receive suchdata from, or provide such data to, another telephone-enabled deviceassociated with the user. In some embodiments, such data transfer can bemade to or from an external database (e.g., a cloud server) which isitself not a telephone-enabled device.

Input/output devices 40 enable device 10 to receive inputs from andprovide outputs to users of device 10. Devices 40 in one embodimentinclude display 20 (e.g., a touchscreen display, etc.), buttons 22(e.g., one or more soft or hard buttons, etc.), speaker 24, microphone26, and other devices 60. Processing circuit 28 is in one embodimentconfigured to receive inputs from any or all of these components, andmay further include voice recognition capabilities, text to speechfunctionality, and the like.

Referring further to FIGS. 1-3, in some embodiments, processing circuit28 is configured to prioritize multiple callers (e.g., callers havingplaced telephone calls to device 10 or a telephone device coupled todevice 10). For each call, processing circuit 28 receives or accessescall data for the telephone call. Call data includes data related to atelephone call, including a caller name, caller telephone number, callertelephone type (e.g., cell phone or landline), a call time, a call date,related previous calls, and the like. Call data may further include dataregarding a tone of voice of a caller (e.g., indicating the urgency ofthe call) or the content of a message left by the caller. Call data maybe stored in memory 36 or in another suitable location.

In some embodiments, processing circuit 28 is further configured toreceive or access prioritization data. Prioritization data includes datausable to establish a priority for each of a number of callers. Theprioritization data may include any or all of data from prioritizationmodule 38 (e.g., priority list 56) or personal information module 30(e.g., messaging application 42, contacts application 44, calendarapplication 46, social media application 48, and similar data). In oneembodiment, the prioritization data is used to establish an extent towhich each caller and the receiver have a preexisting relationship. Forexample, priority list 56 may provide an indication that the receiverconsiders certain callers higher priority and considers other callerslower priority. As discussed in greater detail above, various types ofdata from personal information module 30 may provide indications of howoften a caller and the receiver speak on the phone, correspond via emailor text messaging, meet in person, interact with common social mediaplatforms, and the like.

Referring to FIG. 8, in one embodiment, processing circuit 28 isconfigured to provide a display of prioritized missed calls. Forexample, processing circuit 28 in one embodiment provides missed callsdisplay 120 via a suitable display of computing device 10. Display 120includes a listing of various missed calls 122. For each missed call122, display 120 includes priority 124, caller name 126, a time/date ofthe missed call 128, and call-back information 130. Other informationcan also be provided, including a caller telephone number, etc. As such,once a receiver of computing device 10 is available, processing circuit28 can provide display 120 along with the information therein. In oneembodiment, processing circuit 28 provides display 120 based onavailability information for a user stored in an electronic calendar orscheduling application (e.g., such that display 120 is provided duringfree time of the user). In other embodiments, processing circuit 28provides display 120 at predetermined times (e.g., user-defined times).In yet further embodiments, one or more fields of display 120 (e.g.,priority number, caller name, etc.) are selectable links such that byselecting the link (e.g., tapping on an area of a touch screen display),a return call is placed to the respective caller.

Referring to FIG. 4, method 70 of prioritizing callers is shownaccording to one embodiment. A telephone call is received (72) butmissed by the receiver. The missed telephone call may be an unansweredcall, or a call answered by an automated messaging service. Call datafor the telephone call is received (74). The call data may include oneor more of a caller name, a caller number, a call time, a call date, andthe like. Call data is in some embodiments accessed from an electroniccontact application based on known call information (e.g., accessing anaddress using a known caller telephone number). The caller isprioritized with respect to any other missed calls/callers (76). In oneembodiment, the caller is prioritized based on the call data and/orprioritization data. Prioritization data includes various types of datathat provides an indication of the relationship between the caller andthe receiver. For example, the caller and receiver may frequentlycommunicate via phone, text, or email, they may have periodicappointments with each other that are reflected on an electroniccalendar, they may share a common last name, employer, etc., and thelike.

Based on the prioritization of the caller, a future time is determinedfor the receiver to respond to the call of the caller (78), i.e., forthe receiver to return the call or for the caller to call again. In someembodiments, the future time is determined based on accessing anelectronic calendar of one or both of the caller and the receiver. Inother embodiments, a receiver can establish predetermined call-backtimes during which the receiver plans to return telephone calls. In yetfurther embodiments, the future time may be determined based on anexpected arrival time at a destination (e.g., in cases where thereceiver is driving in a car, etc.). The destination may be determinedand the future time automatically suggested to the driver. In the caseof urgent calls, the future time may be determined based on an expectedarrival time at an intermediate location (e.g., a rest stop, a nextexit, etc.). The intermediate location may be determined based on acurrent location and/or direction of travel of the user, oralternatively, may be located on a planned travel route to a destinationlocation. The future time may be determined taking into account drivingconditions such as traffic, weather, road blockages, and the like. Insuch cases, as shown in FIG. 9, navigation application 52 may provide anavigation display 140 including map 142. Map 142 includes startinglocation 146, destination location 148, and one or more intermediatelocations 150, 152 along route 144. Based on determining, for example, apresent location and speed of a vehicle along route 144, an expectedarrival time may be determined for the intermediate locations and thedestination location. In turn, based on the priority of the caller, afuture time may be selected appropriately at an intermediate location orthe destination location. In some embodiments, the future time isselected automatically (e.g., by processing circuit 28), while in otherembodiments, processing circuit 28 may generate a request for the userto select one of the locations.

Once the future time is determined, a message is communicated to thecaller indicating the future time when the receiver expects to returnthe call of the caller (79) (alternatively, the message may request thatthe caller call back at the future time). The message may take a varietyof forms, including an automated voice message provided to the callerduring the telephone call placed by the caller, an automated returnmessage (e.g., a telephone call, email, text message, etc.), indicatingthe future time, and so on. Referring to FIG. 7, one embodiment of amessage display 110 showing a message 112 is illustrated. As shown inFIG. 7, message 112 is provided from the receiver to the caller andprovides an indication of a future time at which the receiver willreturn the telephone call of the caller.

Referring now to FIG. 5, method 80 of prioritizing callers is shownaccording to one embodiment. Method 80 is in many respects similar tomethod 70 shown in FIG. 4. A telephone call is received (82). Thetelephone call may be a missed call, or a call answered by an automatedmessaging service. Call data for the telephone call is received (84).The call data may include one or more of a caller name, a caller number,a call time, a call date, and the like. Call data is in some embodimentsaccessed from an electronic contact application based on known callinformation (e.g., a caller telephone number). The caller is prioritizedwith respect to any other missed calls/callers (86). In one embodiment,the caller is prioritized based on the call data and/or prioritizationdata. Prioritization data includes various types of data that providesan indication of the relationship between the caller and the receiver.For example, the caller and receiver may frequently communicate viaphone, text, or email, they may have periodic appointments with eachother that are reflected on an electronic calendar, they may share acommon last name, employer, etc., and the like.

Based on the prioritization of the caller, a future time is determinedfor the receiver to return the call of the caller (88). In someembodiments, the future time is determined based on accessing anelectronic calendar of one or both of the caller and the receiver. Inother embodiments, a receiver can establish predetermined call-backtimes during which the receiver plans to return telephone calls. In yetfurther embodiments, the future time may be determined based on anexpected arrival time at a destination (e.g., in cases where thereceiver is driving in a car, etc.). Alternatively, in the case ofurgent calls, the future time may be determined based on an expectedarrival time at an intermediate location (e.g., a rest stop etc.)located on a planned travel route to a destination location. Once thefuture time is determined, a message is communicated to the receiverindicating the future time when the receiver expects to return the callof the caller (90) (alternatively, the message may request that thecaller call back at the future time).

After prioritizing the caller, previous callers are reprioritized basedon the prioritization of the present caller (90). For example, if thecurrent caller is considered a high priority caller, the current callermay be prioritized above earlier callers. As such, the prioritization,and therefore the future time of an expected return call, of theprevious callers may change based on additional received calls. In caseswhere the prioritization of a previous caller changes the future time ofwhen the receiver expects to return the telephone call, a message iscommunicated to the previous caller indicating a new future time for areturn telephone call (94).

The present disclosure contemplates methods, systems, and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Wheninformation is transferred or provided over a network or anothercommunications connection (either hardwired, wireless, or a combinationof hardwired or wireless) to a machine, the machine properly views theconnection as a machine-readable medium. Thus, any such connection isproperly termed a machine-readable medium. Combinations of the above arealso included within the scope of machine-readable media.Machine-executable instructions include, for example, instructions anddata which cause a general purpose computer, special purpose computer,or special purpose processing machines to perform a certain function orgroup of functions.

Although the figures may show a specific order of method steps, theorder of the steps may differ from what is depicted. Also two or moresteps may be performed concurrently or with partial concurrence. Suchvariation will depend on the software and hardware systems chosen and ondesigner choice. All such variations are within the scope of thedisclosure. Likewise, software implementations could be accomplishedwith standard programming techniques with rule based logic and otherlogic to accomplish the various connection steps, processing steps,comparison steps and decision steps.

While various aspects and embodiments have been disclosed herein, otheraspects and embodiments will be apparent to those skilled in the art.The various aspects and embodiments disclosed herein are for purposes ofillustration and are not intended to be limiting, with the true scopeand spirit being indicated by the following claims.

What is claimed is:
 1. A method of prioritizing multiple callers,comprising: receiving call data regarding a plurality of telephone callsplaced to a computing device, each of the plurality of telephone callsbeing a missed telephone call placed by a caller; prioritizing eachcaller based on at least one of the call data or prioritization data,the prioritization data providing an indication of a relationshipbetween each caller and a receiver associated with the computing device;determining a future time for each caller to speak with the receiverbased on the prioritization of each caller; and transmitting a messageto each caller providing an indication of the future time.
 2. The methodof claim 1, wherein the prioritization data includes at least one ofelectronic contact data, electronic calendar data, and social mediadata, and wherein the call data includes at least one of a caller name,a caller telephone number, a type of telephone caller, a call time, anda call date.
 3. The method of claim 1, wherein the prioritization dataincludes a priority list of caller names.
 4. The method of claim 3,further comprising placing the caller's name on the priority list ofcaller names based on the prioritization of the caller.
 5. The method ofclaim 1, wherein the relationship includes at least one of a familialrelationship, a marital relationship, and a business relationship. 6.The method of claim 1, wherein the electronic contact data includes atleast one of a name and an address from an electronic contact list. 7.The method of claim 1, wherein the electronic contact data includes atarget response time associated with returning calls by the caller. 8.The method of claim 1, wherein the electronic contact data includes atargeted call duration to be allotted for a returned call to the caller.9. The method of claim 1, wherein the electronic contact data includes atag identifying at least one caller as a high priority contact, whereinthe callers are prioritized based on the tag.
 10. The method of claim 1,wherein the electronic calendar data includes an appointment from anelectronic calendar.
 11. The method of claim 1, wherein the social mediadata includes data linking each caller and the receiver on a socialmedia website.
 12. The method of claim 1, wherein the prioritizationdata includes data related to one or more physical visits between eachcaller and the receiver.
 13. The method of claim 1, wherein theprioritization data includes data regarding a current distance betweeneach caller and the computing device.
 14. The method of claim 1, furthercomprising determining the future time based on scheduling data.
 15. Themethod of claim 14, wherein the scheduling data provides an indicationof free time on an electronic calendar of the caller.
 16. The method ofclaim 14, wherein the scheduling data includes a predicted time ofarrival at intermediate location between a current location of thecomputing device and a destination location during movement of thecomputing device.
 17. The method of claim 1, further comprisingtransmitting messages to previous callers based on reprioritizing theprevious callers.
 18. A method of prioritizing a plurality of callers,comprising: receiving call data regarding a plurality of telephone callsplaced to a mobile computing device, each of the plurality of telephonecalls being a missed telephone call placed by a caller; prioritizingeach caller based on the call data and prioritization data, theprioritization data providing an indication of a relationship betweeneach caller and a receiver associated with the mobile computing device;determining a future time for at least one of the callers to speak withthe receiver based on the prioritization of each caller and a predictedarrival time at an intermediate location located on a planned travelroute to a destination location; and transmitting a message to at leastone of the callers providing an indication of the future time.
 19. Themethod of claim 18, wherein the future time is based on current trafficconditions.
 20. The method of claim 18, wherein the call data providesan indication of at least one of a tone of a voice of a caller and acontent of a message of a caller.
 21. The method of claim 18, whereinthe call data provides an indication of whether a current missed call isplaced by a same caller as a previous missed call.
 22. The method ofclaim 18, further comprising determining the future time based onscheduling data.
 23. The method of claim 22, wherein the scheduling dataprovides an indication of free time on an electronic calendar of thereceiver.
 24. The method of claim 22, wherein the scheduling dataprovides an indication of free time on an electronic calendar of thecaller.
 25. The method of claim 22, wherein the scheduling data includesa predetermined time period for the receiver to return missed telephonecalls.
 26. The method of claim 18, wherein the message includes anelectronic calendar invitation configured to enable each caller topopulate an electronic calendar application of a computing device of thecaller.
 27. The method of claim 18, wherein the message indicates a timewhen the caller should place a future call to the computing device. 28.The method of claim 18, wherein the message indicates a time when thereceiver will place a future call to the caller.
 29. A methodcomprising: receiving call data regarding a plurality of telephone callsplaced to a MOBILE computing device, each of the plurality of telephonecalls being a missed telephone call placed by a caller; determining afuture time for at least one of the callers to speak with the receiverbased on the prioritization of each caller and a predicted arrival timeat an intermediate location located on a planned travel route to adestination location; and transmitting a message to at least one of thecallers providing an indication of the future time.
 30. The method ofclaim 29, wherein the future time is determined based on current trafficconditions.
 31. The method of claim 29, wherein the call data includesat least one of a caller name, a caller telephone number, a type oftelephone caller, a call time, and a call date.
 32. The method of claim29, wherein the call data provides an indication of at least one of atone of a voice of the caller and a content of a message of a caller.33. The method of claim 29, wherein the call data provides an indicationof whether a current missed call is placed by a same caller as aprevious missed call.
 34. The method of claim 29, wherein the methodfurther comprises determining the future time based on scheduling data.35. The method of claim 29, wherein the scheduling data provides anindication of free time on an electronic calendar of the receiver.